

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
<head>
<script type="text/javascript" src="helpman_topicinit.js"></script>

<title>Extending UML [Enterprise Architect User Guide]</title>

<meta name="keywords" content="Enterprise Architect, Sparx Systems, UML, Extending UML,Extending UML With Enterprise Architect,Extending UML And Requirements Management In Enterprise Architect,Extending UML And Business Modeling In Enterprise Architect,Extending UML With UML Patterns In Enterprise Architect,Extending UML With UML Profiles In Enterprise Architect,Extending UML With UML Stereotypes In Enterprise Architect,Extending UML And MDG Technologies,UML,UML Extending">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />

<link type="text/css" href="default.css" rel="stylesheet" />
<style type="text/css">
  A, A:Visited
  {
    color: #00F;
  }

  A:Active, A:Hover
  {
    color: #F00;
  }

  OL
  {
    margin: 5px 0 5px 48px;
  }

  UL
  {
    margin-bottom: 3px;
    margin-top: 0;
  }

  #nsr
  {
    background-color: #D4DFFF;
  }

  #nsr A
  {
    text-decoration: none;
  }

  #mainbody
  {
    padding: 8px;
  }

  .p_BodyText
  {
    padding: 5px 0;
  }
</style>



<style type="text/css" media="screen">
  BODY
  {
    background-color: #FFFFFF;
  }

  #nsr
  {
    padding: 6px 6px 0 6px;
    border-bottom: none;
    vertical-align: top;
    z-index: 2;
    visibility: visible;
    left: 0;
    top: 0;
    position: absolute;
  }

  #mainbody
  {
    left: 0;
    top: 0;
    margin: 0;
    position: absolute;
    padding: 10px;
    overflow: auto;
    height: 100%;
    z-index: 1;
    background-repeat: no-repeat;
    background-position: bottom right;
    background-attachment: fixed;
  }
</style>

<style type="text/css" media="print">
  #nsr
  {
    visibility: none;
  }

  #mainbody
  {
    overflow: visible;
  }
</style>
<script type="text/javascript" language="JavaScript" src="nonscroll.js"></script>

</head>
<body scroll="no">

<div id="page">



        <div id="content">
          <div id="content-inner">
          



  
          <div id="nsr">
            <table border="0" cellspacing="0" cellpadding="4" width="100%">
              <tr valign="top">
                <td align="left">
  


                  <p class="p_Heading1"><span class="f_Heading1">Extending UML</span></p>



  
                </td>
                <td align="right">
                  <a href="introduction.htm" onmouseover="document.images.main.src='button_main_h.gif'" onmouseout="document.images.main.src='button_main.gif'">
                    <img name="main" src="button_main.gif" border=0 alt="Return to Introduction">
                  </a>&nbsp;
    
                  <a href="review_source_and_target_eleme.htm" onmouseover="document.images.prev.src='button_prev_h.gif'" onmouseout="document.images.prev.src='button_prev.gif'">
                    <img name=prev src="button_prev.gif" border=0 alt="Previous page" />
                  </a>&nbsp;
    
    
    
                  <a href="requirementsmanagement2.htm" onmouseover="document.images.next.src='button_next_h.gif'" onmouseout="document.images.next.src='button_next.gif'">
                    <img name=next src="button_next.gif" border=0 alt="Next page" />
                  </a>
    
    
                </td>
              </tr>
            </table>
          </div>
          <div id="mainbody">
  


                <p class="p_TextIndentedL1"><img src="extend_uml.png" width="173" height="100" border="0" alt="extend_uml"></p>
<p class="p_BodyText"><span class="f_BodyText">Enterprise Architect enables you to create models using UML. However, it also enables you to go much further, extending the scope both of your modeling and of the UML components you use, as outlined below.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Requirements Management</span></p>
<p class="p_BodyText"><span class="f_BodyText">Gathering requirements is typically the first step in developing a solution, be it for developing a software application or for detailing a business process. Requirements are essentially 'what the system must do'. The <a href="requirementsmanagement2.htm">requirements management</a> built into Enterprise Architect provides full support for defining, organizing and managing the requirements that drive the project.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">UML Stereotypes</span></p>
<p class="p_BodyText"><span class="f_BodyText" style="font-style: italic;">Stereotypes</span><span class="f_BodyText"> are an inbuilt mechanism for logically extending or altering the meaning, display and syntax of a model element. Different model elements have different standard stereotypes associated with them. You can also define your own stereotypes.</span></p>
<p class="p_BodyText"><span class="f_BodyText">For further information on stereotypes, see the </span><span class="f_BodyText" style="font-style: italic;"><a href="stereotypedlg.htm">UML Stereotypes</a></span><span class="f_BodyText"> topic.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">UML Profiles</span></p>
<p class="p_BodyText"><span class="f_BodyText">UML Profiles are a means of extending UML, which enables you to build models in particular domains. A Profile is a collection of additional stereotypes and Tagged Values applied to elements, attributes, methods and connectors, which together describe some particular modeling problem and facilitate modeling constructs in that domain.</span></p>
<p class="p_BodyText"><span class="f_BodyText">For further information on Profiles, see the </span><span class="f_BodyText" style="font-style: italic;"><a href="umlprofiles.htm">UML Profiles</a></span><span class="f_BodyText"> topic.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">UML Patterns</span></p>
<p class="p_BodyText"><span class="f_BodyText">Patterns are groups of collaborating Objects/Classes that can be abstracted from a general set of modeling scenarios (that is, parameterized collaborations). They generally describe how to solve an abstract problem, and are an excellent means of achieving re-use and building in robustness.</span></p>
<p class="p_BodyText"><span class="f_BodyText">For more information on Patterns, see the </span><span class="f_BodyText" style="font-style: italic;"><a href="umlpatterns.htm">UML Patterns</a></span><span class="f_BodyText"> topic.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">MDG Technologies</span></p>
<p class="p_BodyText"><span class="f_BodyText">The Model Driven Generation (MDG) Technologies enable you to access and use the resources of a specific technology within Enterprise Architect. Interfaces to some technologies, such as BPMN and Iconix, are integrated with Enterprise Architect, whilst interfaces to others such as Eclipse and Visual Studio can be added separately. You can also link to technologies that you have created yourself.</span></p>
<p class="p_BodyText"><span class="f_BodyText">For more information on MDG Technologies, see the </span><span class="f_BodyText" style="font-style: italic;"><a href="mdgtechnologies.htm">MDG Technologies</a></span><span class="f_BodyText"> topic.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Business Modeling</span></p>
<p class="p_BodyText"><span class="f_BodyText"><a href="businessmodelling.htm">Modeling the business process</a> is an essential part of any software development process. It enables you to establish the broad outline and procedures that govern what it is a business does. As the Business Process Model typically has a broader range than just the software system being considered, it also enables you to clearly map what is in the scope of the proposed system and what is to be implemented in other ways.</span></p>




            </div>
          </div>
        </div>



</div>


</body>
</html>
